Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exact match for boundary var attributes #2

Closed
wants to merge 4 commits into from

Conversation

Dave-Allured
Copy link
Owner

@Dave-Allured Dave-Allured commented Dec 1, 2020

Sec. 7.1: Require exact value match for functional attributes on boundary variables.
Issue cf-convention#265

  • Clarify wording and intent of sec. 7.1 on boundary variable attributes.
  • Expand to all data types, not just strings.
  • Clarify that type match is not needed, only compatibility.

Release checklist

  • Authors updated in cf-conventions.adoc?
  • Next version in cf-conventions.adoc up to date? Versioning inspired by SemVer.
  • history.adoc up to date?
  • Conformance document up-to-date?

For maintainers

After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then master always is a draft for the next version.

Sec. 7.1:  Require exact string match for functional attributes on boundary variables.
Issue cf-convention#265
Data type generalization of new wording
Further improve wording.
Another wording improvement
@Dave-Allured Dave-Allured changed the title Sec. 7.1, exact string match for boundary variable attributes 7.1, exact match for boundary var attributes Dec 2, 2020
@Dave-Allured Dave-Allured changed the title 7.1, exact match for boundary var attributes Exact match for boundary var attributes Dec 2, 2020
@Dave-Allured Dave-Allured deleted the 7.1-exact-string-match branch December 2, 2020 02:44
Dave-Allured pushed a commit that referenced this pull request Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant